- Home
- Search Results
- Page 1 of 1
Search for: All records
-
Total Resources4
- Resource Type
-
0004000000000000
- More
- Availability
-
40
- Author / Contributor
- Filter by Author / Creator
-
-
Ramrakhyani, Prakash (4)
-
Alshboul, Mohammad (1)
-
Elsasser, Wendy (1)
-
Esmaeilzadeh, Hadi (1)
-
Harris, Austin (1)
-
Jalali, Ali (1)
-
John, Lizy Kurian (1)
-
Lin, Calvin (1)
-
Mireshghallah, Fatemehsadat (1)
-
Solihin, Yan (1)
-
Taram, Mohammadkazem (1)
-
Tiwari, Mohit (1)
-
Tuck, James (1)
-
Tullsen, Dean (1)
-
Wang, Jiajun (1)
-
Wang, William (1)
-
Wei, Shijia (1)
-
Zhu, Yongye (1)
-
#Tyler Phillips, Kenneth E. (0)
-
#Willis, Ciara (0)
-
- Filter by Editor
-
-
null (1)
-
& Spizer, S. M. (0)
-
& . Spizer, S. (0)
-
& Ahn, J. (0)
-
& Bateiha, S. (0)
-
& Bosch, N. (0)
-
& Brennan K. (0)
-
& Brennan, K. (0)
-
& Chen, B. (0)
-
& Chen, Bodong (0)
-
& Drown, S. (0)
-
& Ferretti, F. (0)
-
& Higgins, A. (0)
-
& J. Peters (0)
-
& Kali, Y. (0)
-
& Ruiz-Arias, P.M. (0)
-
& S. Spitzer (0)
-
& Sahin. I. (0)
-
& Spitzer, S. (0)
-
& Spitzer, S.M. (0)
-
-
Have feedback or suggestions for a way to improve these results?
!
Note: When clicking on a Digital Object Identifier (DOI) number, you will be taken to an external site maintained by the publisher.
Some full text articles may not yet be available without a charge during the embargo (administrative interval).
What is a DOI Number?
Some links on this page may take you to non-federal websites. Their policies may differ from this site.
-
Alshboul, Mohammad; Ramrakhyani, Prakash; Wang, William; Tuck, James; Solihin, Yan (, 2021 IEEE International Symposium on High-Performance Computer Architecture (HPCA))null (Ed.)Non-volatile memory (NVM) is poised to augment or replace DRAM as main memory. With the right abstraction and support, non-volatile main memory (NVMM) can provide an alternative to the storage system to host long-lasting persistent data. However, keeping persistent data in memory requires programs to be written such that data is crash consistent (i.e. it can be recovered after failure). Critical to supporting crash recovery is the guarantee of ordering of when stores become durable with respect to program order. Strict persistency, which requires persist order to coincide with program order of stores, is simple and intuitive but generally thought to be too slow. More relaxed persistency models are available but demand higher programming complexity, e.g. they require the programmer to insert persist barriers correctly in their program. We identify the source of strict persistency inefficiency as the gap between the point of visibility (PoV) which is the cache, and the point of persistency (PoP) which is the memory. In this paper, we propose a new approach to close the PoV/PoP gap which we refer to as Battery-Backed Buffer (BBB). The key idea of BBB is to provide a battery-backed persist buffer (bbPB) in each core next to the L1 data cache (L1D). A store value is allocated in the bbPB as it is written to cache, becoming part of the persistence domain. If a crash occurs, battery ensures bbPB can be fully drained to NVMM. BBB simplifies persistent programming as the programmer does not need to insert persist barriers or flushes. Furthermore, our BBB design achieves nearly identical results to eADR in terms of performance and number of NVMM writes, while requiring two orders of magnitude smaller energy and time to drain.more » « less
-
Mireshghallah, Fatemehsadat; Taram, Mohammadkazem; Ramrakhyani, Prakash; Jalali, Ali; Tullsen, Dean; Esmaeilzadeh, Hadi (, International Conference on Architectural Support for Programming Languages and Operating Systems)
-
Wang, Jiajun; Ramrakhyani, Prakash; Elsasser, Wendy; John, Lizy Kurian (, International Conference on Parallel Architectures and Compilation Techniques (PACT))
An official website of the United States government
